@cs0rbagomba

thanks for addressing this !

BUMP

Some people may want to encrypt a single zvol instead of a pool. That's why git://anongit.gentoo.org/proj/genkernel.git tries to import a zpool before and after luks. So I did it here, trying to unlock before and after luks: alinefr/genkernel-next@489f9fe

We should do both and call start_volumes before and after (need to check if start_volumes is idempotent though).
This because we may discover luks partitions only after start_volumes too.

The lack of integration of the simple fix by @alinefr forces me to use a custom build instead of the repository build... Could this be resolved after almost three years of pending solution? @mudler ?

@ptMuta : I have to use custom genkernel builds too because of this.

Guys, can we have some progress?

start_volumes should be harmless and idempotent, but since this issue have been sitting here for ages we should take action - Let's test, keep it on master and wait later if someone will complain and file bugs ✨

And that's why i said should

Can this please be merged?

It might be fixed already with: 5a1db22

which issues the 2 lines twice:

start_volumes
zfs_start_volumes

setup_keymap

# Initialize LUKS root device except for livecd's
is_livecd || start_luks

start_volumes
zfs_start_volumes

I haven't tasted if works.

I tried it a little while back, but with no success